-
-
Notifications
You must be signed in to change notification settings - Fork 777
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove good second issue 5617 #5682
Remove good second issue 5617 #5682
Conversation
Want to review this pull request? Take a look at this documentation for a step by step guide! From your project repository, check out a new branch and test the changes.
|
Availability: Tuesdays NZT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well done @tkozek on the changes. Changes made were applicable :) Good job!
Review ETA: 10/10/2023 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @tkozek Great job with the issue!
The branching is set up correctly.
You linked the issue.
Changes appear correctly in the test URL. Well done!
Fixes #5617
What changes did you make?
-Removed the following line from CONTRIBUTING.md Section 2.3.c:
*
Prioritized Backlogcolumn in the [filtered Project Board - **complexity: Good second issues** label](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+good+second+issue%22+label%3A%22role%3A+back+end%2Fdevops%22)
Why did you make the changes?
-In order to eliminate confusion, since Hack for LA is no longer creating issues with the "good second issue" label
-For Reviewers: Do not review changes locally, rather, review changes at:
https://github.com/tkozek/website/blob/remove-good-second-issue-5617/CONTRIBUTING.md#23c-available-issues-for-returning-members-back-end
Screenshots of Proposed Changes Of The Website
Before:
After: